I'm seeing failures in the test log starting here: https://github.com/CommunityToolkit/Aspire/actions/runs/21052154522/job/60540747581?pr=1100#step:6:497

The tests themselves don't seem to report failing, so possibly the Assert isn't capturing the stack properly.

Do the test pass locally?

@aaronpowell the problem seems to happen when GetEnvironmentVariablesAsync is called and the tests just 'hang'

I don't mind continuing to work on this, I just need input on why GetEnvironmentVariablesAsync causes the tests to hang.
From what I can tell it's whenever a Postgres integration is also in play

@aaronpowell any input on the GetEnvironmentVariablesAsync?

@dealloc sorry, been under the pump with some other stuff recently. I've just pushed a commit which fixes the timeout issue. I think some of the asserts are now failing though

no worries, just wanted to make sure this PR didn't slip under the radar :)
One of the failing asserts is Assert.Equal("false", env["ZITADEL_TLS_ENABLED"]);

it seems that WithHttpsCertificateConfiguration didn't run yet as I set those vars in the callback.

    [Fact]
    public async Task AddZitadel_Sets_Default_Environment_Variables()
    {
        var builder = DistributedApplication.CreateBuilder();

        var zitadel = builder.AddZitadel("zitadel");

        var env = await zitadel.Resource.GetEnvironmentVariablesAsync();

        Assert.Equal("false", env["ZITADEL_TLS_ENABLED"]);
        Assert.Equal("false", env["ZITADEL_EXTERNALSECURE"]);
        Assert.Equal("zitadel.dev.localhost", env["ZITADEL_EXTERNALDOMAIN"]);
        Assert.Equal("false", env["ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED"]);
        Assert.Equal("false", env["ZITADEL_FIRSTINSTANCE_ORG_HUMAN_PASSWORDCHANGEREQUIRED"]);
    }

I suspect I need to do something so Aspire actually calls the callback for it?